BLINK
BLINK is used in input or menu processes to cause an item to blink on an image.
????? BLINK ??? ?????????????????????? ??? (AT APPEARANCE # ???)
(1) (2) (3) (4) (5)
(1) T/F execution conditions
(2) Application ID
(3) Field name or predefined field
(4) Occurrence (constant/index
(5) Appearance (constant/index)
Using the Statement
BLINK is often used in conjunction with an ERROR or WARNING statement to highlight the fields in error.
The appearance number can be used if the same field appears more than once on the image. If the application ID, field name, occurrence number, and appearance number are not specified (left blank), the BLINK statement affects all of the items painted on the associated image.
BLINK is one of the characteristic-type statements. Refer to the common attributes of all the statements in this category in the Characteristic-Type Statements section of this manual.
The operation of a BLINK statement affects only the next generation of an image. In other words, the item characteristics are reset each time an image is produced.
Restrictions
Note that, because characteristic statements operate on items other than fields, these statements are meaningful only in event points that are associated with an image.
BLINK is a terminal display attribute only and, therefore, is not allowed on images in output processes.
Statement Ignored
The system ignores any BLINK statements specified in non-image-related event points.
Related Statements
BLANK, BOLD, BRIGHT, COLOR, DIM, DISPLAY, ERROR, FONT, INVERSE, NO BOLD, NO ULINE, NORMAL, PICTURE, ULINE, WARNING
Example
In the following example, the customer number is verified while entering an order. If the customer is not on file, the corresponding customer number on the order blinks.
SET TAR CUSTOMER NO = TAR ORDER CUSTOMER NO
READ TAR CUSTOMER HOLD 0 FT 0 BY CUSTOMER NO
F BLINK TAR ORDER CUSTOMER NO (AT APPEARANCE # )
F DISPLAY TAR ORDER CUSTOMER NO (AT APPEARANCE #) |